Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

updated requirements #106

Merged
merged 5 commits into from Nov 9, 2023
Merged

updated requirements #106

merged 5 commits into from Nov 9, 2023

Conversation

darrellodonnell
Copy link
Collaborator

in process of getting requirements captured and migrated (from v1).

Copy link
Contributor

@andorsk andorsk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should add some language around Assurance Levels.

- ii. An **authorized verifier**, including:
a. The **presentation type URI** that an **authorized verifier** MUST use for any authorized **presentation request**.
- i. all `authorization` values that are used by the trust registry.
- ii. all Assurance Levels, specified with unique names, that are service by the trust registry.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is an Assurance Level?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assurance level for what? We should reference a suitable standard if we're to state this. The assurance level is a tricky one IMO because 'assurance level' may be different for different lifecycle stages or in different use cases. See NIST 800-63-3, section 5.2 has three AL's: Identity, Authenticator, Federation.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@andorsk updating ToIP glosarry with a definition. The PCTF defines it as "In the Pan-Canadian Trust Framework™ (PCTF), a Level of Assurance (LoA) represents the level of confidence an Entity may place in the processes and other conformance criteria defined in any given component of the PCTF. Levels of Assurance are elemental in creating networks of trust."

@a-fox assurance levels would be defined in the EGF and be ecosystem-specific.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the "Assurance Level" concept can be offered as something which can be adopted as is or an equivalent in the jurisdiction is adopted. Reminding the reader that LoA is a critical part of this is necessary.

v2/requirements.md Outdated Show resolved Hide resolved
- ii. An **authorized verifier**, including:
a. The **presentation type URI** that an **authorized verifier** MUST use for any authorized **presentation request**.
- i. all `authorization` values that are used by the trust registry.
- ii. all Assurance Levels, specified with unique names, that are service by the trust registry.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assurance level for what? We should reference a suitable standard if we're to state this. The assurance level is a tricky one IMO because 'assurance level' may be different for different lifecycle stages or in different use cases. See NIST 800-63-3, section 5.2 has three AL's: Identity, Authenticator, Federation.

v2/requirements.md Outdated Show resolved Hide resolved
darrellodonnell and others added 3 commits November 9, 2023 06:02
Co-authored-by: Antti Kettunen <antti@identifinity.net>
Co-authored-by: Antti Kettunen <antti@identifinity.net>
@darrellodonnell
Copy link
Collaborator Author

need to create issue about Assurance Levels

@andorsk
Copy link
Contributor

andorsk commented Nov 9, 2023

Discussed at ToIP : Early merge and continue moving on in future PRs. This comments will be addressed in future PRs.

@andorsk andorsk merged commit a087067 into trustoverip:main Nov 9, 2023
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants